-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] [PART-2]vsan stretch testcase automation for TKG, WCP and VMService VMs #3020
base: master
Are you sure you want to change the base?
[WIP] [PART-2]vsan stretch testcase automation for TKG, WCP and VMService VMs #3020
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Aishwarya-Hebbar The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @Aishwarya-Hebbar. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
12b6d7b
to
0caf5b5
Compare
Started GC block pre-checkin pipeline... Build Number: 80 |
0caf5b5
to
1c4b622
Compare
|
Started GC block pre-checkin pipeline... Build Number: 81 |
|
6eed74e
to
8c5cc68
Compare
Started GC block pre-checkin pipeline... Build Number: 82 |
|
8c5cc68
to
fbacdaf
Compare
Started GC block pre-checkin pipeline... Build Number: 83 |
|
e88a301
to
2b8e8c2
Compare
Started GC block pre-checkin pipeline... Build Number: 84 |
2b8e8c2
to
41e82af
Compare
|
41e82af
to
cf78fa5
Compare
274f27d
to
3d2fcd1
Compare
Started GC block pre-checkin pipeline... Build Number: 136 |
3d2fcd1
to
35ec779
Compare
|
35ec779
to
ac0c5b3
Compare
Started GC block pre-checkin pipeline... Build Number: 137 |
|
854d307
to
1e7f30f
Compare
Started GC block pre-checkin pipeline... Build Number: 138 |
|
Started GC block pre-checkin pipeline... Build Number: 139 |
|
Started GC block pre-checkin pipeline... Build Number: 140 |
|
1e7f30f
to
761bf7e
Compare
Started GC block pre-checkin pipeline... Build Number: 141 |
Started GC block pre-checkin pipeline... Build Number: 142 |
|
|
4df2150
to
fc3b3aa
Compare
Started GC block pre-checkin pipeline... Build Number: 14 |
|
Started GC block pre-checkin pipeline... Build Number: 15 |
|
Started GC block pre-checkin pipeline... Build Number: 16 |
|
fc3b3aa
to
5ce54a4
Compare
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Testing done:
A PR must be marked "[WIP]", if no test result is provided. A WIP PR won't be reviewed, nor merged.
The requester can determine a sufficient test, e.g. build for a cosmetic change, E2E test in a predeployed setup, etc.
For new features, new tests should be done, in addition to regression tests.
If jtest is used to trigger precheckin tests, paste the result after jtest completes and remove [WIP] in the PR subject.
The review cycle will start, only after "[WIP]" is removed from the PR subject.
Special notes for your reviewer:
Release note: